Add a runner-PR skill and generalize the PR template#47
Merged
Conversation
Captures the conventions for opening a new-runner pull request (branch name, commit message, PR template, English summary, pre-checklist verification) so future contributors using Claude Code don't have to rediscover them. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Rename `Runner Summary` to `Summary` and add a note that the `Checklist for Adding a Runner` section can be skipped for non-runner PRs (tooling, docs, site changes). Also updates the add-runner-pr skill to reference the new section name. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Kyome22
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Type of Change
Summary
Two related tooling changes:
.claude/skills/add-runner-pr/SKILL.md— a Claude Code skillthat codifies this repository's conventions for opening a
new-runner PR: branch name
add-<name>, commit messageAdd the <name> runner, pre-checklist verification of the ziplayout and
preview.pngdimensions, and reading.github/pull_request_template.mdat PR-creation time (nohardcoded copy in the skill, so it won't drift when the template
changes).
.github/pull_request_template.md— generalized so it fitsnon-runner PRs too.
Runner SummarybecomesSummary, and therunner checklist section carries a note that it can be skipped
when the PR isn't adding a new runner. Previously the template
was runner-specific, which felt awkward for tooling/docs PRs
(this PR itself was the trigger).
Checklist for Adding a Runner